home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The PC-SIG Library 10
/
The PC-Sig Library - Shareware for the IBM PC and Compatibles (PC-SIG)(Tenth Edition Disks 1-2804)(1991).iso
/
PC_SIGCD
/
19
/
9
/
DISK1993.ZIP
/
FILESAFE.EXE
/
UPDATE.DOC
< prev
next >
Wrap
Text File
|
1990-12-10
|
6KB
|
120 lines
F I L E - S A F E
- Updates -
***********
11/90
Version 3.3 has three new features:
When files are displayed for backup selection, you can press "V"
(for View) and the program will display the contents of the file.
This can come in handy when a file suddenly pops up as needing to
be backed up and you didn't know or realize it was there and may
not remember what it contains. You might wish to delete it
rather than back it up.
On this same menu, you now have the option of temporarily
returning to DOS. Simply press the letter "S" (for System) and
you will automatically be presented with the DOS command line
prompt. From here you can check out the contents of other
directories, check on various disk contents, format a new disk,
or perform any other chore you would normally do from DOS. To
return to File-Safe, you simply type in EXIT and press <Enter>.
You will then find yourself right back in File-Safe at the same
place you left it. While in DOS, you can, of course, run any
program or application you wish, but be careful.... the File-Safe
program is in still in memory waiting to resume execution, so the
amount of memory you have available for other programs is
reduced.
When you are in the print catalog section of the program, you
have always had the option of sending the report(s) to the
printer or to a file. Now you can also ask that the report be
displayed immediately on the screen. As explained in the
reference manual, the information in these reports is essentially
the same as what is displayed when you restore files, but it is
formatted differently. When you select this option, the program
generates the report, sends it to a file, and then displays the
file. By doing it this way, you can browse back and forth
through the report rather than being limited to reading forward
through the report file sequentially. On the report which is
sequenced according to the disks on which the backups are stored,
the sizes of the files are also included and totaled. This can
help you keep track of how full various backup disks are.
Numerous parts of the programs have been redone to operate more
efficiently, so now the programs are smaller than they were
before these new features were added.
8/90
Version 3.2 contains several logic corrections, the most
significant of which has to do with the backup process itself.
If you specify that there be no backup directory, the program
would fail with an internal error message. This now works
correctly. However, we still recommend that you use backup
directories as explained in the documentation.
If you make backup copies of files that are marked hidden, read
only, or system, and then try to delete one of them from the
backup catalog, prior versions of the program would say the file
doesn't exist. It now properly finds the file but will not let
you delete it. This would be an extremely rare situation, but if
it should occur, you can use a utility like Xtree, Norton
Utilities, or PC-Tools to change the attribute(s) of the file;
then you can delete the backup file and its corresponding catalog
entry.
The program has been improved in the way it handles multiple
backup disks. When multiple disks are going to be needed, File-
Safe scans the contents of each disk to see if any of the files
being backed up are already on the disk. If they are, those
files get backed up first. This way, the chances of getting
multiple backup copies of any given file on different disks are
reduced.
Prior versions of File-Safe would sometimes not properly display
redefined function keys. Now it does.
8/90
As explained in the documentation, when File-Safe is making
backup copies of files, it records its activity in a temporary
transaction file and then, when it is all done, it uses that file
to update the catalog. If that transaction file gets corrupted
because of a problem with the disk, that update activity could be
aborted because the program thinks it has encountered invalid
records. The program now simply ignores any data it finds which
is invalid.
This recently happened to the author. A four year old 20 mb hard
disk was encountering "seek errors" and File-Safe was being used
to back up additional files in preparation for re-formatting the
disk. The transaction file got "lost" due to a corrupted file
allocation table. When it was restored using DOS RECOVER, the
file had "junk" data appended to it and File-Safe refused to
update the catalog properly. This change corrected the problem.
Also the reformatted disk became good again and all data was
safely restored thanks to File-Safe.
P.S. The errors were apparently occurring in the directory, file
allocation table area and a highly recommended low-level
reformatting utility was unable to fix the problem even though it
reported that everything was ok.
***********